You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, thanks for the helpful project. I'm having an issue using this in a non-Node.js environment (Google Apps scripting), and there's an easy fix, because this project's i/o features are the only issues:
Move all ical parsing code (parseICS) into a new npm module @peterbraden/ical-parser (scope required because unscoped package ical-parser already exists).
Refactor ical to depend on @peterbraden/ical-parser for the parsing logic, but retain the fromURL and parseFile methods for backward compatibility.
If needed, I have already separated the parsing logic myself, and can give it to you in order for you to create @peterbraden/ical-parser. Just let me know if you want it.
That would work, for sure, I just thought you'd want to preserve backward compatibility. Your project, do what you want, but just make sure to rev the major version to remain semver compliant. Thanks!
Hi, thanks for the helpful project. I'm having an issue using this in a non-Node.js environment (Google Apps scripting), and there's an easy fix, because this project's i/o features are the only issues:
parseICS
) into a new npm module@peterbraden/ical-parser
(scope required because unscoped packageical-parser
already exists).ical
to depend on@peterbraden/ical-parser
for the parsing logic, but retain thefromURL
andparseFile
methods for backward compatibility.If needed, I have already separated the parsing logic myself, and can give it to you in order for you to create
@peterbraden/ical-parser
. Just let me know if you want it.NB: Looks like #80 is related to this.
The text was updated successfully, but these errors were encountered: