-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make s-forms compatible with new version of s-forms-editor #145
base: master
Are you sure you want to change the base?
Conversation
… compatibility with s-forms-editor.
✅ Deploy Preview for s-forms-kbss ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No sure about inclusion of styles, see my comments.
@@ -6,7 +6,7 @@ import FormUtils from "../../util/FormUtils"; | |||
import YASQE from "yasgui-yasqe"; | |||
import YATE from "yasgui-yasqe"; | |||
import { ConfigurationContext } from "../../contexts/ConfigurationContext"; | |||
import "@triply/yasgui/build/yasgui.min.css"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@LaChope I am not sure why we do that ... so what are consequences of this decision?
I assume this:
- we did not depend on styling of yasgui component and thus whenever we upgrade new version of yasgui, we need to remember to also generate yasgui.min.css as well
- so what did we get in return? did we need to modify yasgui ? (If so why do we add minified version and not well formated version?)
Minor changed are made to make s-forms compatible with s-forms-editor