Repository navigation
Merge from upstream v2.42.2 - #263
Conversation
…map#12448) Bumps the types group with 1 update: [@types/node](https://github.com/DefinitelyTyped/DefinitelyTyped/tree/HEAD/types/node). Updates `@types/node` from 25.9.1 to 25.9.2 - [Release notes](https://github.com/DefinitelyTyped/DefinitelyTyped/releases) - [Commits](https://github.com/DefinitelyTyped/DefinitelyTyped/commits/HEAD/types/node) --- updated-dependencies: - dependency-name: "@types/node" dependency-version: 25.9.2 dependency-type: direct:development update-type: version-update:semver-patch dependency-group: types ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Bumps [esbuild](https://github.com/evanw/esbuild) from 0.28.0 to 0.28.1. - [Release notes](https://github.com/evanw/esbuild/releases) - [Changelog](https://github.com/evanw/esbuild/blob/main/CHANGELOG.md) - [Commits](evanw/esbuild@v0.28.0...v0.28.1) --- updated-dependencies: - dependency-name: esbuild dependency-version: 0.28.1 dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…ap#12412) landuse=plant_nursery is more similar to landuse=orchard and landuse=vineyard (cultivated agricultural areas) than to natural vegetation like forest/grass. This moves it to the 'Light Green things' group so it renders with a lighter green/yellowish color.
…nstreetmap#12452) Bumps the eslint group with 1 update: [typescript-eslint](https://github.com/typescript-eslint/typescript-eslint/tree/HEAD/packages/typescript-eslint). Updates `typescript-eslint` from 8.60.1 to 8.61.0 - [Release notes](https://github.com/typescript-eslint/typescript-eslint/releases) - [Changelog](https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/typescript-eslint/CHANGELOG.md) - [Commits](https://github.com/typescript-eslint/typescript-eslint/commits/v8.61.0/packages/typescript-eslint) --- updated-dependencies: - dependency-name: typescript-eslint dependency-version: 8.61.0 dependency-type: direct:development update-type: version-update:semver-minor dependency-group: eslint ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
…le (openstreetmap#12453) * Apply a proper intended logic fix for openstreetmap#12129 / openstreetmap#12128 * add test to check intersection-prevention algorithm --------- Co-authored-by: Martin Raifer <martin@raifer.tech>
…map#8724 when multiple primary tags are presence, and only the non-highway one is implying oneway-ness. e.g. for `highway=track + piste:type=downhill` the oneway only applies to the piste sense of the feature, not when interpreted as a highway.
* Add track grade-based styling * Change track styling to be based on grade-only (and not surface) * Increase track casing color lightness slightly * Tweak unpaved roads, bridges and tunnels --------- Co-authored-by: Martin Raifer <martin@raifer.tech>
…map#12406) * Fix uiField not considering sub-tags for multiCombo fields * Fix uiField revert and isModified functions not considering prior matching tags for multiCombo * Add tests for multiCombo field modified checks and undo operation * Add tests for multiCombo field remove operation
…enstreetmap#12467 fixes a crash when hovering over another way while cancelling the drawing of a new way, when the other way has a field that relies on correct contents in `context.selectedIDs`, which are then still containing the outdated reference to the then cancelled way entity
This comment was marked as outdated.
This comment was marked as outdated.
| /** @type {import("geojson").FeatureCollection} */ | ||
| const sources = JSON.parse( | ||
| fs.readFileSync(require.resolve('ohm-editor-layer-index/imagery.json'), 'utf8') | ||
| fs.readFileSync(require.resolve('@openstreetmap/editor-layer-index/imagery.geojson'), 'utf8') | ||
| ); | ||
| /** @type {import("geojson").FeatureCollection} */ | ||
| const ohmSources = JSON.parse( | ||
| fs.readFileSync(require.resolve('ohm-editor-layer-index/imagery.geojson'), 'utf8') | ||
| ); | ||
| sources.features.push(...ohmSources.features); |
There was a problem hiding this comment.
@mradamcox and I think we haven’t been running this script for many releases, if we’ve ever run it. As it was, the script would clobber any upstream imagery in favor of ohm-editor-layer-index build products (which are out of date with respect to the repository’s main branch). Since there was a merge conflict here, I wound up accepting both to combine both upstream and downstream repositories together. This only works because the downstream was eviscerated early on to serve as an overlay of sorts. If we redo that repository to be a more typical fork, then we would need to revisit this code. Either way, we’ll need to rebuild that repository’s build products to reflect the last couple years of PRs merged.
This comment was marked as outdated.
This comment was marked as outdated.
|
Netlify doesn’t seem to associate the deployment with the OHM account there. I would’ve expected the subdomain to reference OHM instead of a randomized slug. Edit: Ah OK, that’s just the Netlify comment. Maybe we can customize that. But the GitHub deployment action also links to https://pr-263--ideditor.netlify.app/ instead of https://pr-263--openhistoricalmap-ideditor.netlify.app/. |
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment was marked as resolved.
This comment comes from the deployment I made from my own netlify account actually, the I think I should just fully delete my deploy, right? Then we'll be back to having the single workflow deployment for previews, but I don't think that integration will provide us with comments on PRs like you see above. |
|
Correct, all we’ll get is a GitHub deployment event like #263 (comment) and the “branch was successfully deployed” box below. |
|
Ah, interesting, so that comment comes from this script, Line 25 in 8b54242 which is run as the final step in the deploy preview workflow: and, as you can see, the original netlify id is hard-coded in there. That's why the "View deployment" button goes to the wrong site. |
|
So I'm going to go ahead and delete my Netlify integration, and then on your end you can update that |
|
OK, the latest deployment status is still busted, but I think that’s only because we haven’t merged this PR yet. Otherwise, can y’all take https://pr-263--openhistoricalmap-ideditor.netlify.app/ for a spin before we merge? Thanks! |
|
|
||
| _this.title = () => { | ||
| // @ts-expect-error -- blocked by OHM-specific id-tagging-schema | ||
| if (field.index) { |
There was a problem hiding this comment.
3a7b61f has my fix, I commited it to a separate branch for now. Once we've setup the OHM-specific id-tagging-schema, we won't need this code anyway
There was a problem hiding this comment.
Ah, #258 removed similar code in favor of resolving stringsCrossReference slightly later on, in an attempt to make it more data-driven. We can pull in your fix though; whatever works in the short term.
mradamcox
left a comment
There was a problem hiding this comment.
Looks great guys, so sorry I missed this review request last week and held us up. Let's do it!
|
|
||
| _this.title = () => { | ||
| // @ts-expect-error -- blocked by OHM-specific id-tagging-schema | ||
| if (field.index) { |

Merged the upstream v2.42.2 tag into the latest OHM staging branch. Upstream is undergoing a piecemeal conversion from JavaScript to TypeScript, introducing merge conflicts that needed more manual review.