hartman / zonestamp Goto Github PK

I want to rewrite this whole thing and get rid of the moment layer.

There are various possibilities, like pure Intl, or date-fns or luton.
The hard part is finding widgets in the associated programming framework that make use of the same frameworks.

Another missing piece was having a list of timezones, but apparently these can be fetched with Intl by using Intl.supportedValuesOf('timeZone')

We lose the timezone name in that case, but that might be acceptable. Another workaround for that:

new Date().toLocaleDateString(undefined, {day:'2-digit',timeZoneName: 'long' }).substring(4);

Make it possible to add translations to zonestamp so that we can serve everyone regardless of language.

There are multiple react-scripts vuln right now. the package doesnt seem to have been updated for over a year (possibly related to ukraine war?).

Should consider ejecting from the tool, and have all dependencies as direct dependencies.

Should add CSS variables for the colors, so that it's easier to switch the color palette.

Steps to reproduce

• Visit https://zonestamp.toolforge.org/
• Pick a date and time (I was using 4th May 2023 17:00 UTC)
• Click "Generate stamp"

What happens?

• URL contains a timestamp that, when converted back to human readable time, ends in a random number of seconds, such as :37 seconds

What should happen instead?

• URL contains a timestamp that, when converted back to human readable time, ends in :00 seconds

Could the switch from a 12 to a 24 hour clock please be made sticky?
This would probably require a cookie. This would work similar as the language settings cookie that is given as an example of the kind of cookie that doesn't require permission in this guide on the gdpr.

request by user @VDK

Create an option to download the time as an ics iCal event

Could also use several arguments from the url like a description ?

I see this in the browser console:

Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

* Move code with side effects to componentDidMount, and set initial state in the constructor.
* Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: BrowserRouter, Route, Router, Switch

react-dom.development.js:88 Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.

* Move data fetching code or side effects to componentDidUpdate.
* If you're updating state whenever props change, refactor your code to use memoization techniques or move it to static getDerivedStateFromProps. Learn more at: https://fb.me/react-derived-state
* Rename componentWillReceiveProps to UNSAFE_componentWillReceiveProps to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run `npx react-codemod rename-unsafe-lifecycles` in your project source folder.

Please update the following components: Route, Router, Switch

Hi! I'm trying to create a new Zonestamp, but when I enter the future date and time, the response is 'invalid date.' My colleague is having the same problem. I've been using the tool reliably for a couple of years and this is the first time I've encountered this issue. Thanks for your help!

Trying to set up zonestamp locally (via git clone; npm install; npm start using node 10.19.0, npm 6.14.4) resulted in

Html Webpack Plugin:
  Error: Child compilation failed:
  Module.createRequire is not a function
  
  - child-compiler.js:169 childCompiler.runAsChild
    [zonestamp]/[html-webpack-plugin]/lib/child-compiler.js:169:18
  
  - Compiler.js:551 finalCallback
    [zonestamp]/[webpack]/lib/Compiler.js:551:5
  
  - Compiler.js:577 compile
    [zonestamp]/[webpack]/lib/Compiler.js:577:11
  
  - Compiler.js:1196 hooks.afterCompile.callAsync.err
    [zonestamp]/[webpack]/lib/Compiler.js:1196:17
  
  
  - Hook.js:18 Hook.CALL_ASYNC_DELEGATE [as _callAsync]
    [zonestamp]/[tapable]/lib/Hook.js:18:14
  
  - Compiler.js:1192 compilation.seal.err
    [zonestamp]/[webpack]/lib/Compiler.js:1192:33
  
  - Compilation.js:2787 finalCallback
    [zonestamp]/[webpack]/lib/Compilation.js:2787:11
  
  - Compilation.js:3092 hooks.afterSeal.callAsync.err
    [zonestamp]/[webpack]/lib/Compilation.js:3092:11

Original hartman/toolforge-deployscript-zonestamp#1 by @tgr

Works: https://zonestamp.toolforge.org/1618671635
Doesn't work: https://zonestamp.toolforge.org/1618671635?fbclid=IwAR3bJL9ows_qdHHrsXwMvBRtErrvBsVdMD8XinrX2k9RE3bV7916Z4Yq_dI

Obviously this is a big problem for sharing events on social media.

Upstream does not seem to have this issue: https://zonestamp.com/1617962599?fbclid=IwAR3bJL9ows_qdHHrsXwMvBRtErrvBsVdMD8XinrX2k9RE3bV7916Z4Yq_dI

Given this zonestamp:

https://zonestamp.toolforge.org/1696521600?enddate=1696525200&name=MCDC+community+open+session&description=Zoom+link:+https://wikimedia.zoom.us/meeting/register/tZcsc-uvrz4pHNyicRTaLYxiGbg1J3Shub9i

the calendar should generate an UTC 16h-17h, but actually it's 10h-10h (the day is correct).

The .ics has
DTSTART;TZID=Etc/GMT:20231005T100000
DTEND;TZID=Etc/GMT:20231005T100000

and also
DTSTART:19700101T000000
which, I don't know much about ics but seems wrong, but I guess that's an unrelated issue with the calendar widget itself.

ebfceda

We had to downgrade because the newer version didn't seem to detect changes to the state of the timezone.

I am creating an event in Montevideo time 18 November at 9.30 local time. It should be 12.30 UTC. The tool shows it correctly. When I export to Google calendar, the event is marked to start at 13.30 Greenwich time, and the event is placed on the schedule at 13.30 UTC. Here's the Zonestamp https://zonestamp.toolforge.org/1700310600

Instead of using moment in english locale, add more locales.

Small problem, how do we add all locales, without blowing up the initial JS size.