delightful-beach-23533
09/12/2022, 2:48 PMdelightful-beach-23533
09/12/2022, 4:10 PMlemon-wall-20836
09/12/2022, 4:10 PMlemon-wall-20836
09/12/2022, 4:10 PMstrong-restaurant-36788
09/12/2022, 4:25 PMstrong-restaurant-36788
09/12/2022, 4:25 PMlemon-wall-20836
09/12/2022, 5:25 PMdelightful-beach-23533
09/15/2022, 3:15 AMlemon-wall-20836
09/15/2022, 6:34 AMloud-jewelry-99127
09/15/2022, 6:58 AMloud-jewelry-99127
09/15/2022, 7:05 AMbright-tomato-27372
09/15/2022, 1:40 PMProduct.where(company_id: current_user.company_id
on their resource index page. Is using Pundit the way to do that? Going to keep looking through docs since I know it's somewhere there ๐wooden-pizza-89220
09/16/2022, 6:05 PMblue-hospital-77159
09/18/2022, 8:16 PMlemon-wall-20836
09/19/2022, 9:18 AMlate-cartoon-17585
09/20/2022, 11:59 AMtall-ghost-95744
09/20/2022, 2:45 PMlate-cartoon-17585
09/20/2022, 2:50 PMwooden-pizza-89220
09/21/2022, 6:33 PMvisible
block for this?/Is it possible?wooden-pizza-89220
09/22/2022, 4:59 PMextra_params
in the custom Resource Tool. The extra parameters I'm sending in the :create
are not ones being saved on my database, but rather, getting JSON-ified in order to send to an AWS Secrets Manager.
In my Resource tool, I have
self.extra_params = [{
the_secrets: %i[some_key some_token some_provider_id some_account_id]
}]
Then, like the docs say, I have a method in my model to parse the hash I'm receiving from `the_secrets`:
def handle_secrets=(value)
@those_secrets = value.to_json
end
The issue is, the extra_params
method seems to be conflicting with the other permit I have for the required params needed for AWS (let's just say they're :name, :type, :id
). I'm seeing two warnings for Unpermitted parameters
with different values. Only one includes the_secrets
hash I created. Does anyone know why this could be happening?
https://docs.avohq.io/2.0/resource-tools.html#add-custom-fields-on-formslemon-wall-20836
09/22/2022, 5:46 PMquaint-pencil-2979
09/28/2022, 8:51 PMripe-article-50191
09/29/2022, 9:24 AMstylesheet_link_tag
and javascript_include_tag
the AVO javascript doesn't work and I have the next message in console:
DOMException: Failed to execute 'define' on 'CustomElementRegistry': the name "turbo-frame" has already been used with this registry
ripe-article-50191
09/29/2022, 9:25 AMripe-article-50191
09/29/2022, 9:29 AMlemon-wall-20836
09/29/2022, 9:29 AMripe-article-50191
09/29/2022, 9:32 AMripe-article-50191
09/29/2022, 10:31 AMripe-article-50191
09/29/2022, 10:48 AMimport './js/my_custom.js
3. - In browser sources tool I am able to see localhost:3000>assets>avo.custom-blahblah1234.js
4. - In this .js file I can see my custom functions function my_function(){...}
but if in my custom new file <script>my_fucntion()</script>
doesn't works. In fact, the console prints Uncaught ReferenceError: my_function is not defined
Any idea?ripe-monitor-54023
09/29/2022, 4:49 PM