No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/ALwrity#640

kerem commented

2026-03-13 21:01:18 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/AJaySi/ALwrity/pull/332
Author: @AJaySi
Created: 2/9/2026
Status: ❌ Closed

Base: main ← Head: codex/fix-persistence-keys-mismatch-in-debug-helper-xuh0r9

📝 Commits (1)

7aacff1 Fix persistence keys and docs

📊 Changes

4 files changed (+20 additions, -18 deletions)

View changed files

📝 backend/models/user_profiles.py (+8 -8)
📝 docs/ALwrity Researcher/RESEARCH_PERSONA_DATA_SOURCES.md (+1 -1)
📝 docs/ALwrity_vision.md (+1 -1)
📝 frontend/src/components/LinkedInWriter/utils/persistenceTest.ts (+10 -8)

📄 Description

Pull Request

📝 Description

Brief description of changes made in this PR.

🔄 Type of Change

🐛 Bug fix (non-breaking change which fixes an issue)
✨ New feature (non-breaking change which adds functionality)
💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
📚 Documentation update
🎨 Style/UI changes
♻️ Code refactoring
⚡ Performance improvements
🧪 Test additions/updates

Closes #(issue number)
Fixes #(issue number)
Related to #(issue number)

🧪 Testing

Backend tests pass
Frontend tests pass
Manual testing completed
Cross-browser testing (if applicable)
Mobile testing (if applicable)

📸 Screenshots (if applicable)

Add screenshots to help explain your changes.

Before

After

🏷️ Component/Feature

Which component or feature is affected?

Blog Writer
SEO Dashboard
Content Planning
Facebook Writer
LinkedIn Writer
Onboarding
Authentication
API
Database
GSC Integration
Subscription System
Monitoring/Billing
Documentation
Other: _______________

📋 Checklist

My code follows the project's style guidelines
I have performed a self-review of my own code
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation
My changes generate no new warnings
I have added tests that prove my fix is effective or that my feature works
New and existing unit tests pass locally with my changes
Any dependent changes have been merged and published

ALwrity-Specific Checklist

API endpoints follow RESTful conventions
AI service integrations handle rate limits and errors gracefully
Content generation includes proper validation and sanitization
Database migrations are included if schema changes are made
Environment variables are documented in env_template.txt
Security considerations have been addressed
Performance impact has been considered
User experience is consistent with existing features

🔍 Code Quality

Code is properly formatted
No console.log statements left in production code
Error handling is implemented where needed
Performance considerations have been addressed
Security considerations have been addressed

📚 Documentation

README updated (if needed)
API documentation updated (if needed)
Code comments added for complex logic
Changelog updated (if applicable)

🚀 Deployment Notes

Any special deployment considerations or environment variables needed.

🔗 Additional Context

Add any other context about the pull request here.

👥 Reviewers

Tag specific reviewers if needed:
@AJaySi @uniqueumesh @DikshaDisciplines

Thank you for contributing to ALwrity! 🎉

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/AJaySi/ALwrity/pull/332 **Author:** [@AJaySi](https://github.com/AJaySi) **Created:** 2/9/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `codex/fix-persistence-keys-mismatch-in-debug-helper-xuh0r9` --- ### 📝 Commits (1) - [`7aacff1`](https://github.com/AJaySi/ALwrity/commit/7aacff1158e4cb678b975233725a70da83210ad9) Fix persistence keys and docs ### 📊 Changes **4 files changed** (+20 additions, -18 deletions) <details> <summary>View changed files</summary> 📝 `backend/models/user_profiles.py` (+8 -8) 📝 `docs/ALwrity Researcher/RESEARCH_PERSONA_DATA_SOURCES.md` (+1 -1) 📝 `docs/ALwrity_vision.md` (+1 -1) 📝 `frontend/src/components/LinkedInWriter/utils/persistenceTest.ts` (+10 -8) </details> ### 📄 Description # Pull Request ## 📝 Description Brief description of changes made in this PR. ## 🔄 Type of Change - [ ] 🐛 Bug fix (non-breaking change which fixes an issue) - [ ] ✨ New feature (non-breaking change which adds functionality) - [ ] 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] 📚 Documentation update - [ ] 🎨 Style/UI changes - [ ] ♻️ Code refactoring - [ ] ⚡ Performance improvements - [ ] 🧪 Test additions/updates ## 🎯 Related Issues Closes #(issue number) Fixes #(issue number) Related to #(issue number) ## 🧪 Testing - [ ] Backend tests pass - [ ] Frontend tests pass - [ ] Manual testing completed - [ ] Cross-browser testing (if applicable) - [ ] Mobile testing (if applicable) ## 📸 Screenshots (if applicable) Add screenshots to help explain your changes. ### Before  ### After  ## 🏷️ Component/Feature Which component or feature is affected? - [ ] Blog Writer - [ ] SEO Dashboard - [ ] Content Planning - [ ] Facebook Writer - [ ] LinkedIn Writer - [ ] Onboarding - [ ] Authentication - [ ] API - [ ] Database - [ ] GSC Integration - [ ] Subscription System - [ ] Monitoring/Billing - [ ] Documentation - [ ] Other: _______________ ## 📋 Checklist - [ ] My code follows the project's style guidelines - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] Any dependent changes have been merged and published ### ALwrity-Specific Checklist - [ ] API endpoints follow RESTful conventions - [ ] AI service integrations handle rate limits and errors gracefully - [ ] Content generation includes proper validation and sanitization - [ ] Database migrations are included if schema changes are made - [ ] Environment variables are documented in env_template.txt - [ ] Security considerations have been addressed - [ ] Performance impact has been considered - [ ] User experience is consistent with existing features ## 🔍 Code Quality - [ ] Code is properly formatted - [ ] No console.log statements left in production code - [ ] Error handling is implemented where needed - [ ] Performance considerations have been addressed - [ ] Security considerations have been addressed ## 📚 Documentation - [ ] README updated (if needed) - [ ] API documentation updated (if needed) - [ ] Code comments added for complex logic - [ ] Changelog updated (if applicable) ## 🚀 Deployment Notes Any special deployment considerations or environment variables needed. ## 🔗 Additional Context Add any other context about the pull request here. ## 👥 Reviewers Tag specific reviewers if needed: @AJaySi @uniqueumesh @DikshaDisciplines --- **Thank you for contributing to ALwrity!** 🎉 --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

closed this issue
added the
pull-request
label

Rows
Columns

[PR #332] [CLOSED] Fix persistence keys and docs #640