-
Notifications
You must be signed in to change notification settings - Fork 0
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
GSLUX-733: Symbols #147
GSLUX-733: Symbols #147
Conversation
GitHub Pages links: * Luxembourg-geoportail: https://geoportail-luxembourg.github.io/luxembourg-geoportail/GSLUX-733-point-symbole/ |
b81ed39
to
05af2bf
Compare
994ea61
to
5f96327
Compare
5f96327
to
2c68677
Compare
f098f8a
to
9e05cf8
Compare
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.
Thanks @AlitaBernachot for this clean implementation!
# Paths for symbols | ||
VITE_SYMBOL_ICONS_URL="https://map.geoportail.lu/mymaps" | ||
VITE_SYMBOLS_URL="https://map.geoportail.lu/mymaps/symbols" |
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.
Shouldn't we rather use the migration URLs for dev and staging?
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.
It would be better I agree but there are currently CORS issues when calling https://migration.geoportail.lu/mymaps/symbols
in dev, should I change to migration anyway? (it can be bypassed using a chrome plugin but you have to be aware of that. What do you think?
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.
I will merge as is for the demo, there is surely something to do with the url from migration/prod for the symbols, especially for the upload symbols functionality.
inject('currentEditCompKey') | ||
// const feature: DrawFeature | undefined = inject('feature') // TODO: | ||
const featureShape: FeatureShape = 'circle' // feature.olFeature.get('shape') // TODO: to plug when feature ok | ||
const featureColor = 'red' // feature.olFeature.get('color') // TODO: to plug when feature ok |
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.
This will be part of the logical part anyway, but did I understand right, that the problem of using DrawnFeature.featureStyle.color
here is, that it currently needs a DrawnFeature.changed()
call for ol
to update it?
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.
Exactly, we should improve Drawnfeature class to avoid calling ol functionalities in our components.
0c14a8e
to
bfcca3f
Compare
JIRA issue
https://jira.camptocamp.com/browse/GSLUX-733
Description
Implement symbol edition for Point (UI only).